Periodic Functions Available to Schedule
Purpose: The tables below provide a list of the periodic functions you can use to schedule certain functions in Order Management System.
See How to Schedule a Job for information on how to schedule a periodic process.
• General Usage (ALL) Periodic Functions
• Customer Service (C/S) Periodic Functions
• E-Commerce (EDC) Periodic Functions
• Fulfillment (FUL) Periodic Functions
• Interface (INT) Periodic Functions to Start and Stop IJCT Jobs
• Additional Interface (INT) Periodic Functions
• Inventory (INV) Periodic Functions
• Order Entry (O/E) Periodic Functions
General Usage (ALL) Periodic Functions
The table below lists the periodic functions associated with General Usage processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
General Usage Periodic Functions |
||||
Function |
Program |
Parameter |
Schedule |
Description |
AUTHALL |
PFR0131 |
|
As needed |
Authorize All Open Orders Calls Performing Batch Authorization (SATH), which processes online authorizations for all open orders that contain a credit card or stored value card payment that requires authorization. This periodic function allows you to use the job scheduler to schedule when you wish to process the Batch Authorization Program (SATH). |
BO_REAS |
PFR0024 |
|
Daily |
Evaluate Backorder Reasons without Backorder Warehouse Tries to reserve order detail lines that have a backorder reason, but no backorder warehouse. If inventory is not available, this function assigns a backorder warehouse so that the order detail line will process through Evaluate Backorders. See Working with the EBO_ASYNC Job. If an order line on backorder is reserved, the system determines whether the order line is eligible for pick slip preparation; see Preparing Orders for Pick Slip Generation. |
BROKER |
PFR0083 |
|
As needed |
Generate Order Broker Requests Generates Order Broker requests for currently eligible orders that have not previously been submitted to the Order Broker. You might use this function when you are first starting to use the Order Broker integration, or on a periodic basis to generate requests for backordered lines that were not previously eligible because, for instance, the order was held. See the Order Broker Integration for an overview. |
CLR_MTH |
MSR0576 |
|
Monthly |
Monthly Clear Process Clears (updates the zero) the MTD (month-to-date) fields in all tables. Tables affected include Picker Error History, Picker/Packer, Flash Report, Item Warehouse, Location, Picker Error History. |
PFR0200 |
DB FROM TO Y/N where: DB is the owner of the database. FROM is the From company number TO is the To company number Y/N is a Y or N setting indicating whether the system should delete the data in the To company before copying. Unless you can verify that you are not copying over any records that already exist in the target company, this setting should be set to N. Note: Separate each parameter setting with a single space. |
|
Uses the following parameters to create a company: • the owner of the database. • the From company number whose data you wish to copy. • the To company number. • Y or N setting indicating whether the system should delete the data in the To company before copying. Note: Separate each parameter setting with a single space. For example, enter the following in the Parameter field, where DB is the database owner, 1 is the From company number, 2 is the To company number, and N is the Delete To company parameter: DB 1 2 N . Delete Company To use this periodic function to delete a company, enter the company you wish to delete in the From and To company parameters and set the Delete parameter to Y. For example, enter the following in the Parameter field, where DB is the database owner, 1 is the company you wish to delete, and Y is the Delete parameter: DB 1 1 Y |
|
PFR0121 |
Number of hours The system deletes all active procedures for interactive jobs that are older than the number of hours defined. If you do not define a number of hours, the default number of hours is 24. |
Daily |
Delete Stranded Active Procedures Deletes active procedures for interactive jobs that are older than the number of hours defined in the Parameter field. If you leave the Parameter field blank, the system deletes active procedures for interactive jobs that are older than 24 hours. Which interactive jobs? When you run this periodic function, the system checks the Active Procedures table to see if there are any active records for the following applications: • Order Entry/Maintenance • Purchase Order Maintenance • Receiving • Confirmation • PC Manifest or the Generic Pick In API (Shipments, Voids, and Backorders) The system compares the Date and Time in the Active Procedure table against the date and time when you run this periodic function to determine which active procedure records for interactive jobs to delete. |
|
|
|
|
|
Note: Do not run this periodic function while users are still using the applications listed above. If you delete Active Procedures records while a user is still in the application, the user job will not be ended; that user can still enter transactions in the application, but transaction records cannot be sent to the data queues for processing because the data queues are reorganized when the ASYNC jobs end. No back end table updates for that user's transactions will be posted, which will cause your data tables to be out of sync. |
DLYCLR |
MSR0574 |
|
Daily |
Clear Daily Journals • Clears (updates to 0) all daily buckets. • Clears (updates to 0) the TD (today) fields in all tables. Tables affected include Flash Report, Division, Item Warehouse, Order Type/User, Picker/Packer, Ship Via. You should run daily reports before executing this periodic function. Add this function as the last one (or just before reorganizing data tables) in a daily periodic process. |
DSHPROC |
FLRDSHP |
|
Daily |
Processes all drop ship orders by vendor, and generates vendor drop ship worksheet, purchase orders and invoices, or pick slips. Output depends on the Drop ship output selection in the Second Create Vendor Screen. You can also submit this process on demand at the Select Vendors for Drop Ship Screen. |
DSLJPAY |
ACR0315 |
|
Daily |
Daily Sales Journal by Pay Type Generates the Daily Sales Journal by Pay Type. |
DSLJRN |
ACR0216 |
|
Daily |
Daily Sales Journal Generates the Daily Sales Journal. |
ECOMERR |
ECR0295 |
|
Daily |
Batch OM Transaction Error Listing Generates the E-Commerce Order Maintenance Errors Report. See Working with Batch Order Maintenance Transactions (WBOM). |
ENDASYN |
MSENDASYNC |
|
Daily |
End Asyncs If the asyncs are currently Active, this periodic function calls the Controlling Data Queue (CNTL_ASYNC) in Background Job Control (MBJC) and ends the background jobs. This periodic function performs the same updates as selecting End for the controlling data queue to end the background jobs; however, any records in the data queue will be processed when the background ASYNC jobs are restarted. See Ending the Background ASYNC Jobs for more information on the updates that are performed. |
ILENDGENER |
The Process ID for the integration layer process you wish to end. |
As needed |
Ends the integration layer process whose Process ID is defined in the Parameter field. Example: If you define ITEM_OUT in the Parameter field, this periodic function ends the ITEM_OUT integration layer process. |
|
FUTURE |
FLR0246 |
|
Daily |
Evaluates and reserves orders. If the arrival date - lead days = today’s date, then the system reserves the stock and updates the Future order flag to N. If the order is reserved and updated to an open status, the system determines whether the order is eligible for pick slip preparation; see Preparing Orders for Pick Slip Generation. |
JOBCLN |
PFJOBCLNUP |
Set the parameter to: • Y to perform logging only without cleaning up the jobs, or • N to clean up the jobs as well as logging. |
After server restart |
The function: • Sets any jobs in Job Management that are in a MSG status to END. • Sets the CDC job to INACTIVE if it is in any other status. • Sets all IJCT jobs to INACTIVE if they are in any other status, except for the jobs set to INTERACT. • Reorganizes the data queue and then sets all MBJC jobs to INACTIVE if they are in any other status. • Deletes any active procedures (MACX). • Uses the user name that submitted the periodic process to end the process. If you use the CWServiceIn message with a message type of CWProcessIn to submit the request, these requirements apply to the default user (typically named the DEFAULTUSR). • Writes messages to the log as this periodic function is run and what changes were made to clean up the jobs. The user submitting this function must have admin and security user authority and a rank of 1. Note: If you run this function by submitting it through the CWProcessIn SOAP service or the ProcessIn REST service, the wait_for_completion flag should be set to N. |
MDADRCG |
CSX1069 |
|
Daily |
Marketing Download Address Change Report Generates the Marketing Download Change of Address Interface Report when you submit a periodic process that also includes the Marketing Download Extract. |
MDCSCHG |
CSX1061 |
|
Daily |
Marketing Download Customer Status Change Report Generates the Marketing Download Customer Status Change Interface Report when you submit a periodic process that also includes the Marketing Download Extract. |
MDEXTR |
CSX1041 |
|
Daily |
Extracts information from the Marketing Download Trigger table and populates the Marketing Download order-related and customer-related tables, based on the setting of the Populate Marketing Download Trigger File (G33) system control value. Once populated, deletes the associated records in the Marketing Download Trigger table. |
MDEXPRT |
PFR0130 |
|
Daily |
Marketing Download Export Exports the data in the Marketing Download order-related and customer-related tables to pipe-delimited files and places the files in either the Marketing folder of the directory defined in the CWDIRECTCP_ FTP_FOLDER property or the OMS-MARKETING container of the FILE_STORAGE table, depending on whether the File Storage API is enabled. Once the extract files are created, the system deletes the records in the associated Marketing Download tables. |
MDINQSM |
CSX1066 |
|
Daily |
Marketing Download Inquiry Summary Report Generates the Marketing Download Customer Inquiry Interface Report when you submit a periodic process that also includes the Marketing Download Extract. |
MDORDHD |
CSX1044 |
|
Daily |
Marketing Download Order Header Report Generates the Marketing Download Order Header Interface Summary Report when you submit a periodic process that also includes the Marketing Download Extract. |
MDORDTL |
CSX1058 |
|
Daily |
Marketing Download Order Detail Change Report Generates the Marketing Download Order Detail Interface Summary Report when you submit a periodic process that also includes the Marketing Download Extract. |
MDSRCSM |
CSX1036 |
|
Daily |
Marketing Download Source Summary Report This download is no longer supported. |
ONHAND |
PFR0005 |
|
Monthly |
On Hand by Warehouse Generates the On Hand by Warehouse Report. |
OMS-OKM |
PFR0135 |
|
As needed |
OMS to OKM Switch Encryption Key Performs an encryption key switch, replacing the Order Management System Cloud Service encryption key with an OMS Key Management encryption key and encrypting credit card numbers in non-order related tables using the new OMS Key Management encryption key. The system stores the alias used to retrieve the OMS Key Management encryption key in the OKM_ACCESS_ALIAS property. Note: Run this periodic function instead of using the Encryption - Generate Key Switch (CESK) menu option. You must still use the Encrypt Credit Card Order Batch (ECOB) menu option to encrypt credit card numbers in order related tables. See the Data Security and Encryption Guide for more information. |
OMS-OKM |
PFR0135 |
|
As needed |
OMS to OKM Switch Encryption Key Performs an encryption key switch, replacing the Order Management System encryption key with an OKM encryption key and encrypting credit card numbers in non-order related tables using the new OKM encryption key. The system stores the alias used to retrieve the OKM encryption key in the OKM_ACCESS_ALIAS property. When the process completes, the system generates the NonOrder CC Encryption Convert report, listing the tables that the system encrypted successfully. If the non-order key switch did not complete successfully, use the Encryption - Switch Key Non-Order Conversion (CESN) menu option to restart the non-order key switch in the location where the process left off. Once the key switch process is complete, set the OKM_KEY_SWITCH_TYPE and OKM_ACCESS_ALIAS_SWITCH properties to blank, remove the Order Management System keys stored locally, and set the Use Credit Card Encryption (I97) system control value to Y. Note: Run this periodic function instead of using the Encryption - Generate Key Switch (CESK) menu option. You must still use the Encrypt Credit Card Order Batch (ECOB) menu option to encrypt credit card numbers in order related tables. See the Data Security and Encryption Guide. |
ORDSUM |
PFR0062 |
|
Daily |
Order Summary • Updates all of the fields defined in the Order Control Summary table for the current transaction date. See Reviewing Operations Control Summary (FLSH). • Updates the actual value fields and Last updated fields defined in the Threshold Values table. See Working with Threshold Values (WTHR). • Generates the Operations Control Report. Note: This periodic function performs updates similar to the THRESHD periodic function. |
CSSDOUT |
|
Daily |
Sold Out Processing Generates the soldout notifications. .You can also submit this process on demand through the Generating Soldout Notifications (MSON). |
|
PFPOSX |
|
As needed |
POSLOG for XLink Generates and sends a custom POSLog to Xlink using the POSLOG XLink properties, or places it in the OMS-POSLOG container in the FILE_STORAGE table if the file storage API is enabled for exports. See the File Storage API for background, and see the XLINK_DIRECTORY_ARCHIVE_PATH and additional related properties for configuration options. Note: To use this periodic function, you need to have a valid store number specified in the Default Location for ORCE Integration (K69) system control value. Also, you need to set up the store location in Work with Store Cross Reference (WSCR). |
|
PRMOUPL |
PRMOUPL |
|
|
Create or Delete Promotions Creates or updates promotions and related tables based on the information in the Promotion Upload table. See Promotion Upload for more information. |
PSJD |
ACR0321 |
|
Daily |
Print Sales Journal by Division Generates the Sales Journal by Division. |
PURGECS |
PFR0137 |
The number of days old the sold to customer must be to be eligible for purge. The system uses the last change date to determine the age of the customer sold to record. |
Daily |
Purge Sold To Customers Purges sold to customers that are older than the number of days specified. If the Parameter is blank or 0, records must be 365 days old to be eligible for purge. To be eligible for purge, the system verifies that: • there are no open orders for the customer. • there are no open refunds for the customer. • there are no open returns for the customer. • there is no open A/R for the customer. • there are no open ticklers for the customer. • there are no catalog requests for the customer. • there are no open memberships for the customer. See Purging Sold To Customers for background and for the list of tables that are purged. |
PFR0114 |
Set the parameter to Y in order to generate the Purged Order List; otherwise, the report is not generated. |
Daily |
Purge Orders Purges orders that are closed or canceled, and that: • have not had any activity for the Order Purge Days (C62) defined in the System Control table. For example, if the purge days is 365, a closed or canceled order will be eligible for purging if the order has not been entered, shipped, or maintained for one year. The system checks the Order Transaction History table for the most recent activity. • do not have any pending returns or refunds. See Purging Orders (MPOR) for background and for the list of order-related tables that are purged. |
|
PURGEUA |
PFR0125 |
The number of days old a User Audit or Password Audit record must be to be eligible for purge. |
Daily |
Purge User Audit Table Purges User Audit and Password Audit records that are older than the number of days specified. If the Parameter is blank or 0, records must be 365 days old to be eligible for purge. See Tracking User, Authority, and Password Updates for background. |
PFR0126 |
The number of days old a Upload History record must be to be eligible for purge. |
Daily |
Purges Upload History records that are older than the number of days specified in the Parameter field. If the Parameter is blank or 0, records must be 21 days old to be eligible for purge. See Work with File Uploads (WUPL) for more information. |
|
RESET |
MSR0698 |
|
Run when a problem is detected
Note: Run this function only when you have a dedicated system; do not run this periodic function when the Billing Async is active, you are running pick slip generation or performing inventory transaction processing. |
• Resets the reserved quantity of items in inventory, as stored in the Item Warehouse table. The system uses the information in the Reserved Order Line table to determine the correct quantities of items reserved on open or held orders. See Reset Reserve Quantity (MRQR). • Resets the backorder quantity of items in inventory, as stored in the Item Warehouse table. See Reset Backorder Quantity (MRBO). • Resets the SKU open quantity, On hold quantity, and Quantity order direct ship in the SKU table based on the current open orders for the SKU. See Reset SKU Open Order Quantity (MRSO). Note: You can use Reset Allocation Quantities (MRPC) to reset the printed quantities for orders, as stored in the Order Detail, Reserved Order Line and the Item Location tables. The system uses the information in the Pick Control Detail and the Pick Location tables to determine the correct quantities. |
RESETOH |
PFR0093 |
|
Run when a problem is detected. |
Resets the quantity on-hand for each Item Warehouse record based on the total quantities on-hand for related Item Locations within the warehouse. See Reset Item Warehouse Quantity On Hand (MRIW). Note: Run this function only when you have a dedicated system; do not run this periodic function when the Billing Async is active, you are running pick slip generation or performing inventory transaction processing. |
PFR0133 |
|
Daily |
Send Reversals for Expired Authorizations Processes all open Authorization History records that are eligible for authorization reversal processing. Note: Run this periodic function daily so that expired authorizations are reversed in a timely manner without incurring penalty fees. When you run this periodic function for a specified company, the system: • Selects all open (Status is A or O) Authorization History records whose pay type is eligible for authorization reversal (the Send reversal field for the pay type is selected). • For each record selected, the system calculates the age of the authorization by determining the elapsed days between the current date and the authorization date. • If the elapsed days is equal to or greater than the Reauthorization days defined for the pay type, and the authorization service defined for the pay type allows authorization reversals (the Send reversal for the authorization service is selected), the system sends an authorization reversal request to the authorization service. |
|
|
|
|
|
• The system creates an Authorization History Reversal record to indicate that the authorization reversal request was attempted. If the authorization service accepts the reversal request, the system updates the record with the date of the approval. See What Happens When the Authorization Reversal is Approved? and What Happens When the Authorization Reversal is Declined?. |
RFRECON |
PFR0008 |
|
Monthly |
Refund Reconciliation and Purge Purges refund checks once you have reconciled or voided the checks. Generates the Check Reconciliation List. |
RLTITMF |
PFR0101 |
|
Daily |
Oracle Retail Customer Engagement Item Feed Sends item information to Oracle Retail Customer Engagement. See Oracle Retail Customer Engagement Item Feed. |
RLTSLSF |
PFR0102 |
|
Daily |
Oracle Retail Customer Engagement Sales Feed Sends sales information to Oracle Retail Customer Engagement. See Oracle Retail Customer Engagement Sales Feed. |
RSLTME |
CSR0557 |
|
Daily |
Releases prepaid orders from hold automatically when the number of days to hold the order (in the Hold days field in the Pay Type table) has passed, and releases orders held for credit card authorization. |
PFR0090 |
Positions 1-3: 3 position Authorization service code Positions 4-10: 7 position Purchases transactions to generate For example, where AUT is the authorization service code and 1234567 is the maximum number of deposits for purchases: AUT1234567 |
Daily |
Schedule Deposits Submits the deposit processing job. You can use the Parameter field to generate deposit transactions for a specific authorization service and/or define the maximum number of deposits to process for purchases. Note: You can define a Purchases transactions to generate number in the Parameter field only if the Preload Deposits (L78) system control value is unselected. If you do not define any parameters, the system uses the same settings as if you used the Auto Deposit Screen (Send or Receive Deposits) with all the default settings selected. This function requires you to specify a company when you set up the periodic process. |
|
|
|
|
|
The AUTO_DEP job selects records from the Invoice Payment Method table for the service bureau(s) selected for deposit that have not yet been processed for deposit or credit, and whose deposit release date is the current date or earlier. You can review the submitted AUTO_DEP job at the Job Management Screen. See Processing Deposits for more information. |
SCVREV |
PFR0077 |
|
Daily |
Stored Value Card Reversal Processes stored value card reversal trigger records (File type AHR) that are in a ready (R) status. See Transmitting Activation and Reversal Transactions (SSVC). |
PFR0087 |
|
Daily |
Remove credit card data from closed or cancelled orders Removes credit card numbers and expiration dates, deactivates pay types, and sets the Amount to charge to $.01 for closed or cancelled orders whose last order activity was older than the Credit Card Retention Days (K65) system control value. |
|
SLSSMOT |
PFSLSSUMOT |
Date, in MMDDYY format |
Daily |
Sales Journal Summary by Order Type Generates the Sales Journal Summary by Order Type for the date specified in the parameter. If no date is specified, generates the report for the previous date. |
SLSUPLD |
PFR0109 |
|
As needed |
Sales Associate Upload Upload a Sales Associate file to create records in the Salesman table. See Salesman Associate Upload. |
STOP_EC |
ECX0243 |
|
Daily |
Stops the ORDER_CLN job. |
STRASYN |
MSSTRASYNC |
|
Daily |
Start Asyncs If the asyncs are currently Inactive, this periodic function calls the Controlling Data Queue (CNTL_ASYNC) in Background Job Control (MBJC) and starts the background jobs. This periodic function performs the same updates as selecting Start for the controlling data queue to start the background jobs. |
ILSTRGENER |
The Process ID of the integration layer process you wish to start. |
As needed |
Starts the integration layer process whose Process ID is defined in the Parameter field. Example: If you define ITEM_OUT in the Parameter field, this periodic function starts the ITEM_OUT integration layer process. |
|
ILSTRPMD |
|
Daily |
Starts the PMD_ONLINE job in Working with Integration Layer Processes (IJCT). When started, the PMD_ONLINE job opens a connection to the online port used for the Paymentech Point-to-Point Integration. Note: The Paymentech integration is not currently implemented. |
|
ENDPMD |
ILENDPMD |
|
Daily |
Stops the PMD_ONLINE job in Working with Integration Layer Processes (IJCT). When stopped, the PMD_ONLINE job closes the connection to the online port used for the Paymentech Point-to-Point Integration. Note: The Paymentech integration is not currently implemented. |
STRT_EC |
ECX0242 |
|
Daily |
Start E-Commerce Order Cleanup Starts the ORDER_CLN job. |
SUSPEND |
OER0756 |
|
Daily |
Suspended Orders List |
SVCACT |
PFR0076 |
|
Daily |
Stored Value Card Activation Processes stored value card activation trigger records (File type SVC) that are in a ready (R) status. See Transmitting Activation and Reversal Transactions (SSVC). |
SYNCUSR |
PFRSYNUSR |
|
Daily |
Synchronize Users from IDCS Create user records in Order Management System based on user records in IDCS, using the settings defined for the DEFAULTCSU user. See User Configuration in the Administration Guide for more information. Note: You should schedule the function to run daily, or include the function in multiple periodic processes to run more than once a day, in order to keep user records in Order Management System synchronized with IDCS. |
THRESHD |
PFTHRESHMO |
|
Daily |
Threshold Monitor • Updates all of the fields defined in the Order Control Summary table for the current transaction date.See Reviewing Operations Control Summary (FLSH). • Updates the actual value fields and Last updated fields defined in the Threshold Values table. • Monitors the threshold values to determine if a threshold has been breached. • For each breached threshold that has an email address defined and whose Email interval is reached, generates a Threshold Monitor Breach email. • Updates the actual value fields and Last updated fields defined in the Threshold Values table. • Monitors the threshold values to determine if a threshold has been breached. See Working with Threshold Values (WTHR). Note: This periodic function performs updates similar to the ORDSUM periodic function. |
TICKLER |
PFR0072 |
|
Daily |
Evaluate Create/Resolve Ticklers Evaluates the: • OO tickler event to determine if any open orders qualify for an OO event rule. Also, determines if any existing OO ticklers can be resolved. See OO (Aged Open Orders) Event Processing. • UP tickler event to determine if any unconfirmed pick tickets qualify for a UP event rule. Also, determines if any existing UP ticklers can be resolved.See UP (Unconfirmed Pick Tickets) Event Processing. • Next notification date for an existing open or in process tickler to determine if the system sends an email to the tickler supervisor notifying him of the aged tickler. |
UPACSTP |
PFR0134 |
CSACST |
As needed |
UPACSTP Upload ACS Tape File Uploads an ACS Tape file named CSACST from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the ACS Tape table (CSACST). You must use the Process Address Changes (PACS) menu option to process the records in the ACS Tape table. See Work with File Uploads (WUPL) and Loading Address Updates. |
UPCATRQ |
PFR0134 |
IXCRIN |
As needed |
UPCATRQ Upload Catalog Request File Uploads a Catalog Request file named IXCRIN from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Catalog Request Interface table (IXCRIN). You must use the Work with Catalog Request Interface (WCRU) menu option to process the records in the Catalog Request Interface table. See Work with File Uploads (WUPL) and Working with the Catalog Request Interface (WCRU). |
UPCSTPG |
PFR0134 |
CUSTPGEUP |
As needed |
UPCSTPG Upload Customer Price Group Exclusion File Uploads a Customer Price Group Exclusion file named CUSTPGEUP from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Customer Price Group SKU Exclusion Upload table (CUSTPGEUP). You must run the CPGIXUP Customer Price Group SKU Exclusion Upload periodic function (Program name PFRCPGEXUP) to process the records in the Customer Price Group SKU Exclusion Upload table. See Work with File Uploads (WUPL) and Customer Price Group SKU Exclusion Upload. |
PFR0094 |
|
As needed |
Supporting Data Upload Creates supporting data records based on the information in the Supporting Data Upload table. See Importing Item-Related Supporting Data (SDUP) for more information. |
|
PFR0095 |
|
As needed |
Set Component Upload Creates set headers and components based on the information in the Set Component Upload table. See Importing Set Components (WCUP) for more information. |
|
UMPBSTP |
PFR0134 |
CSMBST |
As needed |
UPMBSTP Upload MBS Tape file Uploads an MBS Tape file named CSMBST from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the MBS Tape table (CSMBST). You must use the Process Address Changes (PACS) menu option to process the records in the MBS Tape table. See Work with File Uploads (WUPL) and Loading Address Updates. |
UPPOLAY |
PFR0134 |
POLAYR |
As needed |
UPPOLAY Upload PO Layering File Uploads a PO Layering file named POLAYR from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the PO Layering table (POLAYR) and then uses the newly uploaded records to update the due date and backorder quantity for order lines on backorder. See Work with File Uploads (WUPL) and Purchase Order Layering. |
UPPRCCD |
PFR0134 |
PRICECDUPLOAD |
As needed |
UPPRCCD Upload Price Code File Uploads a Price Code file named PRICECDUPLOAD from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Price Code Upload Table (PriceCdUpload). You must run the PCUPLD Price Code Upload periodic function (Program name PFPRCCODUP) to process the records in the Price Code Upload table. |
UPPROMO |
PFR0134 |
PRMUPLD |
As needed |
UPPROMO Upload Promotion Code File Uploads a Promotion file named PRMUPLD from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Promotion Upload Table (PRMUPLD). You must run the PRMOUPL Create or Delete Promotions periodic function (Program name PRMOUPL) or use the Work with Promotion Values (WPRO) menu option to process the records in the Promotion Upload table. |
UPRITEM |
PFR0134 |
RIIUPP |
As needed |
UPRITEM Upload Retail Item File Uploads a Retail Integration Item file named RIIUPP from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the RI Item Upload Table (RIIUPP). You must run the RIUPLD Retail Integration Item Upload periodic function (Program name PFR0084) or use the Work with Retail Integration Item Upload (RIIU) menu option to process the records in the RI Item Upload table. See Work with File Uploads (WUPL) and Working with Retail Integration Item Upload (RIIU). |
UPSETCM |
PFR0134 |
INSCUP |
As needed |
UPSETCM Upload Set Component File Uploads a Set Component file named INSCUP from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Set Component Upload Table (INSCUP). You must run the UPLSETS Set Component Upload periodic function (Program name PFR0095) or use the Work with Set Component Upload (WCUP) menu option to process the records in the Set Component Upload table. See Work with File Uploads (WUPL) and Importing Set Components (WCUP). |
UPSRCCD |
PFR0134 |
IXSRCE |
As needed |
UPSRCCD Upload Source Code File Uploads a Source Code file named IXSRCE from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Source Upload Table (IXSRCE). You must use the Work with Source Code Upload (WSRW) menu option to process the records in the Source Code Work table. See Work with File Uploads (WUPL) and Generating Source Codes Using the Source Upload Table (WSRW). |
UTSTSRP |
UTSTSRPT |
|
As needed |
Managed Services Report Generates the Managed Services report, used by Oracle staff to manage system processing. |
UPVENDR |
PFR0134 |
VNDUPL |
As needed |
UPVENDR Upload Vendor File Uploads a Vendor file named VNDUPL from the folder defined in the CWDIRECTCP_UPLOAD_DIRECTORY property to the Vendor Upload Table (VNDUPL). You must run the VNDUPLD Vendor Upload periodic function (Program name PFR0086) or use the Submit Vendor Upload (LVUP) menu option to process the records in the Vendor Upload table. |
WEEKCLR |
MSR0575 |
|
Weekly |
Weekly Clear Clears week-to-date (WTD) fields in the SKU Offer Page table (INSKOP). |
YEARCLR |
MSR0577 |
|
Yearly |
Clear Yearly Totals Clears (zeros) yearly (YTD) buckets in tables such as Flash Report table (FLFLSH). |
Customer Service (C/S) Periodic Functions
The table below lists the periodic functions associated with Customer Service processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Customer Service Periodic Functions |
||||
Function |
Program |
Parameter |
Schedule |
Description |
MEMBER |
PFR0036 |
|
Daily |
Generate Membership Orders Generates orders for all standard customer memberships. |
OPENPP |
PFR0006 |
|
Monthly |
Generates the Open Prepaid Order List. |
PFR0115 |
|
Daily |
Process Credit Card Credit Refunds Process credit card credits with no limit on the amount to generate. The system generates a Credit Card Credit Register that identifies the amount, customer name, and order number of each credit processed. The system also produces either a Credit Card Credit Acknowledgment (if the Print Credit Card Credit Acknowledgments (C35) system control value is selected) or an email notification when the Credit Card Credit Acknowledgement E-Mail Program (H08) is set to CCCNOTF, (regardless of the setting of the Print Credit Card Credit Acknowledgments (C35) value) for each credit as appropriate; see When Does the System Generate an Email Notification? See Processing Refunds (MREF) for processing information. |
|
REFDUET |
CSR0986 |
|
Monthly |
Generates the Refund Due List by Type. |
REFPROC |
CSR0533 |
|
Monthly |
Generates the Processed Refund Register. |
PFR0118 |
|
Daily |
Process stored value card credits with no limit on the amount to generate. The system issues a new stored value card to the sold to customer for the refund amount. The system also: • Produces the Stored Value Card Credit Register. • Writes an order transaction history message: F Stored Value Card refund created. • Adds the stored value card item defined in the Default SVC Refund Item Number (I73) system control value to the order at no charge and performs pick slip preparation. Note: The system will not generate a stored value card refund unless the stored value card refund item has available inventory. If the item does not have available inventory, the stored value card refund remains unprocessed. • Generates a pick slip for the stored value card item if the Default Pick Generation Template for SVC Refund Processing (I75) system control value indicates a pick slip generation template. You can then follow the normal process of activating, billing, and shipping the stored value card to the customer. See Generating Stored Value Card Refunds for an overview. |
|
REFWRO |
PFR0009 |
|
Monthly |
Writes off refunds and generates the Refund/Write Offs - Refund Checks report. See Working with Refunds, Writeoffs and Balances Due (WREF). |
RSTCONO |
CSRSTONORD |
|
Run when a problem is detected |
Reset Customer Sold To Amount On Order Resets the On order amount field in the Customer Sold To Order History table so that it matches the amount of any existing open orders for the customer. See Resetting Customer Sold To Amount On Order (RONO). Note: End all background async jobs so that the On order amount is not changed while the reset job recalculates the On order amount. |
UNACTSV |
PFR0075 |
|
Daily |
Unactivated Stored Value Cards Generates the Unactivated Stored Value Card Report. You can use this report to review any stored value cards that require attention because: • the stored value card was declined by the service bureau for activation • the stored value card was billed at the manifest station without a number assignment |
EMAILUD |
PFR0089 |
|
Daily |
Customer Email Status Updates Matches a record in the Customer Email Updates Table to a sold to customer and, if an exact match is found, updates the sold to customer’s Opt in/opt out field with the Email Status defined for the customer email updates record. Generates the Unmatched Email Status Report, which lists records in the Customer Email Updates table that were not matched to a sold to customer. See Receiving Customer Email Status Updates From an External System for an overview and the required setup. |
E-Commerce (EDC) Periodic Functions
The table below lists the periodic functions associated with Customer Service processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
E-Commerce Periodic Functions |
||||
Function |
Program |
Parameter |
Schedule |
Description |
ECOMINV |
ECR0389 |
|
Daily |
E-Commerce Item XRef All Items Downloads all items that contain a long SKU style number to the EC SKU Retail XRef table and EComm SKU Extract table. |
ECOMNEW |
ECR0390 |
|
Daily |
E-Commerce Item XRef New Items Downloads new items that contain a long SKU style number to the EC SKU Retail XRef table and EComm SKU Extract table. |
ECSHCNF |
ECR0154 |
|
Daily |
Shipment Confirmation Emails Sends shipment confirmation emails. |
Fulfillment (FUL) Periodic Functions
The table below lists the periodic functions associated with Fulfillment processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Fulfillment Periodic Functions |
||||
Function |
Program |
Parameter |
Schedule |
Description |
Description of the pick slip generation template you wish to run |
PFR0107 |
The Description of the pick slip generation template you wish to run. Note: The Parameter must match the Description defined for the pick slip generation template. For example, if the description of the pick slip generation template is ORDER #, the parameter must also be ORDER # and not ORDER#. |
Daily |
Scheduled Pick Slip Generation Runs pick slip generation using the pick slip generation template specified in the Parameter field. See Scheduling Pick Slip Generation for more information. |
CARRYOV |
PFR0033 |
|
|
Carryover Report Prints the Carryover Report. |
LOBSTAT |
PFR0034 |
|
Daily |
Reset Line of Business Stats Updates line of business order queue statistics. |
RESRVBO |
FLR0804 |
|
Daily |
Evaluates backorders by searching for any item warehouse that has a backorder quantity greater than 1 and whose on-hand quantity - reserved quantity is greater than 0. Will try to reserve the order detail line (as long as a cancel date does not exist). See Working with the EBO_ASYNC Job. If an order line on backorder is reserved, the system removes any pick slip preparation from the order and then reevaluates the order for pick slip preparation; see Preparing Orders for Pick Slip Generation. |
PFR0111 |
|
As needed |
Reset Pick Control Resets the printed quantities for orders, as stored in the Order Detail, Reserved Order Line and the Item Location tables. The system uses the information in the Pick Control Detail and the Pick Location tables to determine the correct quantities. You can also perform the same updates using the Reset Allocation Quantities (MRPC) menu option. |
|
ILStrCDC |
|
Daily |
Start CDC Job in WPBJ Starts the CDC Async job used to process transactions between Order Broker’s Drop Ship Manager and Order Management System in the Order Broker Drop Ship Integration. |
|
ILEndCDC |
|
Daily |
End CDC Job in WPBJ Ends the CDC Async job used to process transactions between Order Broker’s Drop Ship Manager and Order Management System in the Order Broker Drop Ship Integration. |
|
PACKPRG |
FLPCKPRG |
|
Monthly |
Purge Packer Statistics Purges records in the Packer Productivity table based on the setting of the Packer Productivity Purge Days (K33) system control value. |
PURGPCL |
PFR0091 |
|
Weekly |
Purge Unused Pick Control Labels Submits the PURGPCL job, which: • Purges all unused Pick Control Label records prior to the date you entered in the Unused Pick Label Purge Days (K83) system control value that are not associated with an outstanding pick slip. The system checks the Pick Control Header table to verify that an outstanding pick slip does not exist for the Pick Control Label record. • Purges the associated records in the Pick Out table. |
BILLUPD |
PFR0100 |
|
Daily |
Delay Billing Updates Submits the BILLUPD job, which processes deferred billing updates for records in the Invoice Header table whose Process Date field is 0. You must run the Delay Billing Updates Process if you select the Delay Billing Updates (K85) system control value; see this system control value for more information. Also, see Batch Billing Updates for a table that lists the billing updates that are deferred until you run the Delay Billing Updates Process. Note: You can also submit the Delay Billing Updates Process using the BILL_UPD Billing Updates integration layer job. When this job is active, at defined intervals the job processes deferred billing updates for records in the Invoice Header table whose Process Date field is 0. The Outbound delay time defined for the BILL_UPD integration layer job defines how often the job processes the deferred billing updates. Example: If the Outbound delay time is 60, the system looks for deferred billing updates to process every 60 seconds. |
PICKRFH |
PFR0103 |
|
Daily |
Submits a process that evaluates orders for pick slip preparation, and if eligible: 1. Removes any pick slip preparation that may have already occurred for the order; see Removing Pick Slip Preparation from an Order for the updates that are performed. 2. Applies pick slip preparation to the order; see Applying Pick Slip Preparation to an Order for the updates that are performed. See Batch Pick Slip Preparation for additional details. |
Interface (INT) Periodic Functions to Start and Stop IJCT Jobs
The table below lists the periodic functions provided for starting and stopping IJCT jobs on a regular basis. Each “start” program starts the related IJCT job if it is currently inactive, while each “end” job ends the job if it is currently active. You would normally schedule these jobs to start and stop on a daily basis, but this schedule may vary based on your business requirements.
See Working with Integration Layer Processes (IJCT) for more information on each IJCT job.
Interface Start and Stop Periodic Functions |
|||
Start Function |
Start Program |
End Function |
End Program |
BILL_UPD: Processes deferred billing updates for records in the Invoice Header table whose Process Date field is 0. The Outbound delay time defines how often, in seconds, the job processes the deferred billing updates. |
|||
STRBILL |
ILRSTRBILLUPD |
ENDBILL |
ILRENDBILLUPD |
BROKER: Generates Order Broker requests, inquiry requests, and update (cancel requests, and receives responses. |
|||
STRBROK |
ILSTRBROKR |
ENDBROK |
ILENDBROKR |
CCAUTH_BTH: Sends and receives batch authorizations for credit cards, debit (Switch) cards, and stored value cards transactions to the service bureau via an integration layer process (IJCT). |
|||
STRBAUT |
ILSTRCCBTH |
ENDBAUT |
ILENDCCBTH |
CCAUTH_ONL: Sends and receives online authorizations for credit cards, debit (Switch) cards, and stored value cards transactions to the service bureau via an integration layer process (IJCT). |
|||
STRONLI |
ILSTRCCONL |
ENDONLI |
ILENDCCONL |
DEPOSITS: Sends and receives batch deposits for credit cards, debit (Switch) cards, and stored value cards transactions to the service bureau via an integration layer process (IJCT). |
|||
STRCCDP |
ILSTRDEPST |
ENDCCDP |
ILENDDEPST |
CUST_OUT: Generates an outbound message for each customer that you create, change, or delete. |
|||
STRCSTD |
LSTRCSTOT |
ENDCSTD |
ILENDCSTOT |
CUST_SRCH: Receives a request for information on one or more customers matching specific search criteria, and generates a response. |
|||
STRCSRC |
ILSTRCSTSR |
ENDCSRC |
ILENDCSTSR |
CUST_HIST: Receives a request for customer order history or information on a specific order, and generates a response. |
|||
STRCHST |
ILSTRCSTHT |
ENDCHST |
ILENDCSTHT |
CUSTOMER_IN: Receives a new customer or change to an existing customer. |
|||
STRCSIN |
ILSTRCSTIN |
ENDCSIN |
ILENDCSTIN |
EMAIL: Receives email messages and creates Correspondence History and Correspondence History Detail records. |
|||
STREML |
ILSTREMLIN |
ENDEML |
ILENDEMLIN |
INV_INQURY: Receives a request for inventory availability on a specific item/SKU and generates a response. |
|||
STINVIQ |
ILSTRINVIQ |
ENINVIQ |
ILENDINVIQ |
INV_DOWNLD: Sends inventory availability information to another system. |
|||
STRINVD |
ILSTRINVDN |
ENDINVD |
ILENDINVDN |
INVOIC_OUT: Sends invoice information to another system. |
|||
STRINVO |
ILSTRINVOT |
ENDINVO |
ILENDINVOT |
INVTRAN_IN: Receives inventory transactions and updates inventory information, such as in the Item Location and Item Warehouse tables. |
|||
STRITRN |
ILSTRINVIN |
ENDITRN |
ILENDINVIN |
ITEM_OUT: Sends item and SKU information to another system. |
|||
STRITEM |
ILSTRITMOT |
ENDITEM |
ILENDITMOT |
ORDER_IN: Receives new orders through a generic order interface and optionally generates detailed or simple acknowledgements, as indicated by the inbound order message. |
|||
STRORDR |
ILSTRORDIN |
ENDORDR |
ILENDORDIN |
PICK_OUT: Sends a pick slip message for each generated or voided pick slip. |
|||
STRPICK |
ILStrPickO |
ENDPICK |
ILEndPickO |
PO_OUT: Sends purchase order information to an external system. |
|||
STRPOOU |
ILStrPOOut |
ENDPOOU |
ILEndPOOut |
RETURN_IN: Receives a request to process a return, and generates a response indicating whether the return processed correctly. |
|||
STRRTIN |
ILStrRtnIn |
ENDRTIN |
ILEndRtnIn |
RETURN_OUT: Sends customer return information to an external system. |
|||
STRRTO |
ILStrRtOut |
ENDRTO |
ILEndRtOut |
SVC_AUTH: Sends batch stored value card authorization requests to the service bureau via an integration layer process (IJCT) and receives responses. |
|||
STRSVB |
ILStrSVCAu |
ENDSVB |
ILEndSVCAu |
SVC_AUTHOL: Sends online stored value card authorization requests to the service bureau via an integration layer process (IJCT) and receives responses. |
|||
STRSVO |
ILStrSVCAO |
ENDSVO |
ILEndSVCAO |
SVC_DEP: Sends stored value card deposit requests to the service bureau via an integration layer process (IJCT) and receives responses. |
|||
STRSVD |
ILStrSVCDp |
ENDSVD |
ILEndSVCDp |
SVC_OUT: Sends stored value card activation requests to the service bureau via an integration layer process (IJCT) and receives responses. |
|||
STRSVA |
ILStrSVCOt |
ENDSVA |
ILEndSVCOt |
SVC_REVRSL: Sends stored value card reversal transactions to the service bureau via an integration layer process (IJCT) and receives responses. |
|||
STRSVR |
ILStrSVCRv |
ENDSVR |
ILEndSVCRv |
VENDOR_OUT: Sends vendor information to another system. |
|||
STRVEND |
ILSTRVNDOT |
ENDVEND |
ILENDVNDOT |
WORKFLOW: Receives new workflow events to create ticklers. |
|||
STRWRKF |
ILStrWrkFl |
ENDWRKF |
ILEndWrkFl |
Additional Interface (INT) Periodic Functions
The table below lists additional periodic functions associated with integration layer processing besides those listed above under Interface (INT) Periodic Functions to Start and Stop IJCT Jobs. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Interface Periodic Functions |
||||
Function |
Program |
Parameter |
Schedule |
Description |
PFCAINV |
|
As needed |
ChannelAdvisor Inventory Upload Generates a file of current inventory levels for FTP to ChannelAdvisor. See Sending Current Inventory Information to ChannelAdvisor for an overview. |
|
PFCAOUP |
|
As needed |
ChannelAdvisor Order Upload Sends ChannelAdvisor a request for new orders and creates orders based on the information in the order response message. See Importing Orders from ChannelAdvisor for an overview. |
|
PFCAPRICE |
|
|
ChannelAdvisor Price Upload Generates a file of current pricing for items sold through the ChannelAdvisor integration. See Sending Current Prices to ChannelAdvisor for an overview. |
|
PFRCAREQS |
Enter connection information using the following format: REQUEST ChannelAdvisor_AccountID ChannelAdvisor_ProfileID For example: STATUS cb12d3b4-f123-1234-1234-12a3c456e7d8 12345678 |
As needed |
ChannelAdvisor Request Access Run this periodic function to request access to ChannelAdvisor for the specified AccountID. Before running this periodic function, enter connection information in the Parameter field using the following format: REQUEST ChannelAdvisor_AccountID ChannelAdvisor_ProfileID For example: STATUS cb12d3b4-f123-1234-1234-12a3c456e7d8 12345678 Note: This periodic function should be run one time for each account as part of initial setup of the ChannelAdvisor integration. In addition, once you establish a connection with ChannelAdvisor, you can change the Parameter field to the following format: STATUS ChannelAdvisor_AccountID ChannelAdvisor_ProfileID For example: STATUS cb12d3b4-f123-1234-1234-12a3c456e7d8 12345678 Run the periodic function to write information to the Application log about the status of the access to ChannelAdvisor. See ChannelAdvisor Setup. |
|
PFCASHIP |
|
As needed |
ChannelAdvisor Ship Confirmation Upload Sends shipment confirmation messages to Channel Advisor. See Sending Shipment Confirmations to ChannelAdvisor for an overview. |
|
CPGIXUP |
PFRCPGEXUP |
|
Daily |
Customer Price Group SKU Exclusion Upload Submits the Customer Price Group SKU Exclusion Upload Process to upload customer price group item exclusion information from an external system to create, update, or delete records in the Customer Price Group SKU Exclusion table. See Customer Price Group SKU Exclusion Upload for an overview. |
CSTDWNL |
PFRCSTDNLD |
|
Daily |
Mass Customer Download Generates a batch file that contains a Mass Customer Download XML Message (CWCustomerDownload) for each sold to customer whose customer class matches the customer class defined in the MASS_CUSTDWNLD_CUSTOMER_CLASSES setting in Working with Customer Properties (PROP). See Mass Customer Download for more information. |
PFCYBDMUP |
|
Daily |
Cybersource Decision Manager Update Run this periodic function to receive the Fraud Decision assigned to orders that received a REVIEW Cybersource Decision Manager Fraud Score response during online authorization processing. Based on the Fraud Decision received from Cybersource, the system: • If the Fraud Decision assigned to the order is ACCEPT, releases the order from FS Fraud Scoring Hold. • If the Fraud Decision assigned to the order is REJECT, and no part of the order has been shipped, cancel the order using the cancel reason code in the Fraud Score Cancel Reason Code (M14) system control value. If the entire order cannot be cancelled, place the order on FC Fraud Cancellation Hold. The system writes an order transaction history message noting the response received from Cybersource Decision Manager. Any review comments returned from Cybersource are stored on the order as an order message. See Cybersource Decision Manager Fraud Scoring for additional information. |
|
IHDWOIT |
PFR0106 |
|
As needed |
Invoice Download Comparison Matches invoices created for the previous day to records in the IL Trigger table with a record type of IHD. If an invoice exists without a corresponding IHD trigger, the system creates an Add IHD trigger record and writes a message similar to the following in the Trace log: Periodic Function IHDWOIT may have created a IHD WOIT Transaction for Company#:7 Order # : 2844 Invoice #: 573. See Generic Invoice Download API for an overview on the Invoice Download process and the required setup. |
IMPSTLC |
PFR0122 |
• Position 1 = Set to Y or y if the store cross-reference records should be created with the Ship for Pickup flag selected; otherwise, you would typically set the first position to N. • positions 2-11 = The code identifying the system associated with the locations. Must be a valid system code in Order Broker. Example: If the parameter is set to NPOS, the periodic function imports location records for system POS in Order Broker, and leaves the Ship for pickup flag for each imported location unselected. |
As needed |
Import Store Cross Reference Locations through Order Broker’s Discovery Web Service Uses Order Broker’s discovery web service to request information on all existing location associated with a specified system in Order Broker, and create Store Cross Reference records for locations if they do not already exist. See Importing Store Cross Reference Locations through Order Broker’s Discovery Web Service. |
PFINVOVR |
|
Daily |
Processes an inventory upload file if it is found in the directory defined in the CWDIRECTCP_UPLOAD_DIRECTORY property, updating the Item Location record with the on-hand quantity, or creating it if the Item Warehouse exists. See Batch Inventory Overlay Upload for more information. |
|
INVDWNL |
ILR0081 |
|
Weekly |
Inventory Download Creates inventory download triggers (File type ITW) for an item/SKU if: • the Create Generic Inventory Download Trigger Records (I32) system control value is selected. • the record matches the trigger rules for the INV_DOWNLD process in Integration Layer Job Control (IJCT). • there is at least one Item Warehouse record that matches all criteria. |
OBPROD |
PFR0127 |
|
As needed |
Order Broker Product Output File Generates a Product output file for import into Order Broker. This file contains product information for a specified company. See Order Broker Product Output File for details. |
OBPRLOC |
PFR0128 |
|
As needed |
Order Broker Product Location Output File Generates a Product Location output file for import into Order Broker. This file contains product location information for a specified company. See Order Broker Product Location Output File for details. |
OBINCIN |
PFR0129 |
|
As needed |
Order Broker Incremental Inventory Output File Generates an Incremental Inventory output file for import into Order Broker. This file contains inventory updates for a specified company. See Oracle Retail Order Broker Incremental Inventory Output File for details. |
OCDSFA |
PFR0203 |
|
Daily |
OCDS Import Future Availability Updates the Pre-order flag for pre-order items, and updates item warehouse quantities to support identifying when to release eligible pre-ordered items to Order Broker for fulfillment. See Enterprise Order Integration (Future Receipts and Pre-Order Processing) for background. |
OCDSITM |
PFR0202 |
FULL or INCREMENTAL |
As needed |
OCDS Import Product Data Generates requests to Omnichannel Cloud Data Service OCDS) for item-related data, including merchandise hierarchy, items, item prices, and item images. See Importing Enterprise Foundation Data through Omnichannel Cloud Data Service (OCDS) for details. |
PCUPLD |
PFPRCCODUP |
|
Daily |
Price Code Upload Submits the Price Code Upload Process to upload price code information from an external system to create, update, or delete records in the Price Code, Price Code Customer, and Price Code Details tables. See Price Code Upload for an overview. |
PREORDER |
PFR0204 |
|
Daily |
Submit Pre-Orders to Order Broker and RICS Backorder Message Submits existing pre-orders to Order Broker for fulfillment and generates the pre-order (backorder quantity update) notification message to RICS. See Enterprise Order Integration (Future Receipts and Pre-Order Processing) for background. |
PURGIJT |
ILR0026 |
|
Weekly |
Purge IJCT Trigger Records Purges IL Outbound Trigger records older than the number of days specified in the Outbound Interface Trigger File Purge Days (I14) system control value, using the following calculation: Last processed date is less than the current system date by the number of purge days and Status is X. |
PFREVXAHP |
Stored value card pay type code that uses the External Payment Service |
Daily |
Reverse Partial Auth for External Payment Service Generates SVC reversal request messages for the external payment service, provided the parameter specified is a stored value card pay type code that is configured to use the external payment service. See Stored Value Card Reversal with the External Payment Service in Stored Value Card Authorization Reversal for an overview. |
|
RIPRCUP |
PFRRIPRCUP |
|
Daily |
Pricing Upload Submits the Pricing Upload Process to upload records from the Pricing Upload table to the Special Pricing by Source table and QPM Detail table. See Pricing Upload Interface for an overview. |
RLTCSUP |
PFRBCC |
|
As needed |
Customer Upload to Oracle Retail Customer Engagement Sends all Order Management System sold to customers, excluding any sold to customers whose Ghost field in the Customer Sold To table is Y, to Oracle Retail Customer Engagement using the batch Customer Engagement Add or Update Customer Message. See Customer Engagement Batch Customer Conversion. |
RLTCSID |
PFRCIU |
|
As needed |
Update Customer with Relate ID Updates the Relate ID in the Customer Sold To table with the Customer ID from Oracle Retail Customer Engagement. See Customer Engagement Batch Customer Conversion. |
RLTNOID |
PFRCNI |
|
After running RLTCSID |
Report Customer with No Relate ID Generates a report listing the Order Management System sold to customers that do not have a Relate ID. See Customer Engagement Batch Customer Conversion. |
RMSZIP |
PFRRMS |
store ID and offer code |
As needed |
RMFCS and RPCS Import Uses the contents of the momzip file to create records in the RI Item Upload Table (RIIUPP). See Oracle Retail Merchandising Foundation Cloud Service (RMFCS) and Oracle Retail Pricing Cloud Service (RPCS) Integration. |
RTLOG |
PFR0201 |
Store number in the Sales Audit module of the Oracle Retail Merchandising Foundation Cloud Service |
Daily |
Export Transactions to Sales Audit Module Exports sales and returns information to the Sales Audit module of the Oracle Retail Merchandising Foundation Cloud Service. Transaction information is collected in a temporary file throughout the day. The periodic function adds file header and footer information, deletes the temporary file, and creates a DAT file for the Sales Audit module. See Integration with the Sales Audit Module of the Oracle Retail Merchandising Foundation Cloud Service. |
SLSUPLD |
PFR0109 |
|
Daily |
Upload Salesman Associates Submits the Salesman Associate Upload Process to upload salesman information from an external system to create or update records in the Salesman table. See Salesman Associate Upload for an overview and the required setup. |
STRUPLD |
PFR0110 |
|
Daily |
Upload Stores Submits the Store Upload Process to upload store information from an external system to create or update records in the Store Cross Reference table. See Store Upload for an overview and the required setup. |
SYNCRDB |
PFR0105 |
|
As needed |
Synchronize Remote Customers Submits unsynchronized customers to Oracle Retail Customer Engagement, using the Synchronize with remote DB field in the Customer Sold To table as a trigger. You would use this periodic function to support the interactive customer integration with Oracle Retail Customer Engagement. See Synchronizing Customer Information through a Periodic Function for more information. |
Inventory (INV) Periodic Functions
The table below lists the periodic functions associated with Inventory processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Inventory Periodic Functions |
||||
Function |
Program |
Parameter |
Schedule |
Description |
CLROH99 |
PFRCLROH99 |
|
As needed |
Clear On Hand for Division 99 Allows you to clear the on-hand inventory for each warehouse whose Division is 99. The system clears the on-hand quantity for the warehouse in the Item Warehouse table and Item Location table. |
FGUPDT |
PHR0049 |
|
Monthly
Note: Do not run this periodic function when Asyncs are active. |
• Updates the cost of a finished good when the cost of one or more of its component items changes and generates the Finished Good Items Average or Standard Cost Updated Report. See Updating the Cost of a Finished Good. • Creates an item download trigger. See Generic Item Download API. Note: If a component item changes and you do not run this periodic function, the finished good item cost will not be accurate and reports will not be correct. |
PFR0063 |
PFR0063 |
|
Daily |
Drop Ship On Hold Report Generates the Drop Ship Integration Items on Hold from Vendor report. |
PFR0064 |
PFR0064 |
|
Daily |
Drop Ship Revised Due Date Report Generates the Drop Ship Integration Items with Revised Due Date report. |
PFR0065 |
PFR0065 |
|
Daily |
Drop Ship Pending Cancel Report Generates the Drop Ship Integration Items Pending Cancellation report. |
PORST |
OER1018 |
|
As needed |
PO Reset Resets the open PO quantities in the Item Warehouse table based on purchase order detail lines that are open or held, or received into suspense or into a pending putaway warehouse location. |
PFR0084 |
|
As needed |
Retail Integration Item Upload Submits the retail integration item upload process. Once completed, if the Create Generic Item Download Trigger Records (I15) system control value is selected, the system submits the secondary job RISECU to create item download triggers. See Working with Retail Integration Item Upload (RIIU) and RI Item Upload Process. |
|
UPD_STD |
POR0461 |
|
Monthly
Note: Do not run this periodic function when Asyncs are active. |
Update Standard Cost Updates the cost of all items in the SKU table with the item’s landed cost. The system uses the price defined for the primary vendor plus any additional vendor/item charges to determine the landed cost. The system only updates the standard cost for items with a primary vendor and a vendor item associated with the vendor. The Costing Method (A25) system control value must be set to STANDARD in order to update the standard cost of all items. |
PFR0086 |
|
As needed |
Vendor Upload Submits the vendor upload process. |
Order Entry (O/E) Periodic Functions
The table below lists the periodic functions associated with Order Entry processing. The Parameter column is populated only if the periodic function allows you to define an additional parameter. The Schedule column represents how often you should generally run the periodic function. Your business requirements may require a different schedule.
Order Entry Periodic Functions |
||||
Function |
Program |
Parameter |
Schedule |
Description |
PFR0112 |
The number of days from the promotion end date that a completed promotion will be eligible for purge. Example: promo1 end date = 1/15/12 promo2 end date = 3/18/12 purge days = 15 If you run this periodic function on 3/20/12, the system deletes any promotion with an end date less than 3/5/12. In this example, the system deletes promo1 and retains promo2. |
As needed |
Purge Promotions When you run this periodic function, the system uses the current date - the purge days parameter to determine the promotions to purge. Any promotions whose end date is equal to or earlier than the calculated purge date will be purged. If the Parameter is set to 0, the system does not purge any promotions. The system purges promotions from the following tables: • Promotion • Promotion Discount • Promotion Customer • Promotion Item Exclusion • Promotion BOGO • Promotion Item Category • Promotion Source • Promotion BOGO by Price Code |
|
SUMVIA |
OER1024 |
|
Daily |
Update Ship Via/Item Summary Runs a batch job to collect information on the current number of available order lines for each item/ship via combination in your company and populates the Ship Via Item Summary Header (OESVIH) table and Ship Via Item Summary Detail (OESVID) table. You can review the total open orders, shippable units, and oldest arrival dates for each item with a particular ship via assigned using the Ship Via/Item Inquiry (SVII) menu option. |